Programming Rules

1. Main text editor Notepad Plus Plus
2. Costume language in Notepad Plus Plus allowing for costume text collapse
3. Default text collapse open and close in notepad plus plus is ./. and /./
4. Comment description above everything as if I will not remember anything of the snippet the next time I look at it
5. Write ./. and /./ with each parts of snippet for it to collapse if part is over 3 lines. Exception and very short snippets. Not an iron rule apply by judgement which parts to collapse and how
6. In the case of languages such as c sharp and c a work document is kept at fixed location to test codes. Default editor is Visual Studio
7. C sharp default editor is Visual Studio
8. Default saving of snippets is txt. Then copy pasting them into run files. Exception is jsks
9. New programming snippets are temporarily placed on desktop in groups of the languages till sorted
10. Desktop icons are kept to a minimum this help in motivating me to sort files from desktop to place as it visually unnerves me to see it in a none minimal display
11. Folder on desktop containing blank files per language. Each with appropriate pre written lines at its head
12. Name progressing codes and even designs by version. Starting with 1.0 then incrementing accounting for how big the change or how significant. Whether it is a build on over the old code and so a century decimal or something insignificant and so its plus 0.1. Integers increments are thus on amount of build ons and on significance of build ons. This should result in in better comprehension and retention of what it is I currently have and a vision of where it might get to by version x.
13. Use auto hot key for shortcut for quickly brackets and circle brackets alt , and alt . For the cirle. Alt ; and alt for squiggly
14. Even if knowing a method is temporary and I am going to move on from it there is still value in spending hours in setting up a thing. Like a write to file GUI in python knowing I will move on from python GUI because once its established you guarantee that you will take the time to transfer it to the new working method
15. Always make variables to simplify math operators otherwise you will lose hours every year on putting parenthesis wrong. No exceptions. Even if super simple or it will necessarily be stretched to the loss of hours
16. Daily viewing of a graph of all code snippets bars biggest to smallest. If too many languages split images
17. Make a separate code file for every little code snippet and for all little code snippets to system and all codes by rating and date
18. When making functions with parameters comment in the top line and list with a coma what the parameters refer to in order
19. Postponing designation- develop my own text editor
20. Postponing designation -reconsider relevance of replacement index for code
21. Postponing designation -a Linux costume computer
22. Postponing designation -develop my own programming language
23. Comment above function parameters in format .. A=… b=… also done in case of GUI that writes functions to file
24. Preference of programming language or framework learning is always above all by the online support available. A good measurement is the search of the frame work or such name on stack overflow.
25. Better to copy paste variables than type saving me typing errors and hours of debugging a month
26. In making of variables preference is to similar names such as in case of weekly daily monthly allowing for each alteration once I make a snippets for one of them even in case of 100s of occurrence by a simple search replace daily monthly
27. Default variables writing is with words separate by underscore of descriptive variables
28. Variables above functions are written on different lines allowing me to group them if related like min max
29. Note if random plus minus is used on parameter in its description by +-
30. Unwritten suffix of all programming tasks is to reasonably test the code on completion
31. Software version incarnating number one as 0.1 increment per written update in a version history. No symbolical leap. Per 100. Means more when you look at it
32. Postponing designation- website building GUI like Wix
33. If having a long description break it down to lines. As long as I see one line after the other with nothing in between ill know they are split part of the same description
34. Break down if and or conditions to variables with values of true or false and using the variable in a final if conditional of if true or false
35. Comment above squiggly brackets what they close
36. dispaly boxes are split into small strips each to contain a setnce up to 20 words except the last one to contain reminder allowing me to read sweeping down rather than each time going left to right
37. before a copy paste of a singline line you have to try to manually type and fail. exception when i have no doubt i know how to type it and am just saving time by copy pasting over typing
38. message boxes in polymath other than for debug purposes are by costume pormpt with image for me to develop hints. like picture of a guy in thinking pose on message consdier...
39. by default a small text search box next to new dropdowns created if you expect them to have many values.
40. when using a filtering prompt you have to each time skim one column at a time looking at the image and seeing if you know what its refrencing and if you dont then you have to read its refrence title. you do this each time till you can easily tell what the image is refrencing and then you can just look at the images one column at a time without reading their refrences
41. preferance when looping through mysql table rows to use where filter and limit to only loop through relevant rows and save time
42. on a function arriving at sufficinet complexity make a second grid of sub switches for its sub functions allowing to easily turn them on and off. this is done using a text box getting the function name on its cell selection within the first grid and a button to load its subfunctions switches within the second grid
43. use SQLBackupAndFTP for hourly automatic mysql databases backup
44. weekly functions running at day start load only if day of the week is sunday
45. log start time and end time of all functions into a mysql table to get better awareness of their durations. written as a two liner. first line contains a variable of the title of the function for quick alteration and the second is the update itself. needs to be applied for new code written. i dont have to apply for code already written unless i make some edit to it
46. sqlite for portable databases in .net applications
47. in goals rating the rating of the mother goals is the greatest. above that of the close subgoals. yet still tasks and rules aimed at subgoals get greater priority because the time estimation of sub goals is smaller and so parameters reward them for greater progress contribution. the reason they get higher rating is in case difference in time estimation of them and thier subgoals is small enough so that ill go after the main thing rather than a subgoal
48. portable apps are developed in a seperate visual studio project rather than as part of the main one
49. before code task is considered finished i have to take the entire code and paste it into a text box in a debugging form to establish a habit that would later allow me to apply coding standards
50. on entering deubgger window a prompt that asks for programming langauge. based on selection a button that checks for typos going through every word in text box and a list of function words of that language checking for 1 levenshtein distance errors and changing font of these to red and creating popup of total errors
51. debugger window also serves as a code editor window being able to shut down deubgger fuctions automatically applied to text box by an on off button
52. a special timer meant for manual text edits. if manual text edit exceeds 15 minutes i have to write a function for it that will always be accessible in text editor. place this timer on side bar instead of the 60 minutes timer
53. to make me develop code editor and debugger visual studio forms backups are stored in edtor form rathe thatr in notepad plus plus as i anyway dont use it anymore for edits
54. gui buttons in the same sections have to be of the same size. applies for new forms and when adding buttons to existing forms
55. designated compact code - get visual studio dropdown value in a single line
56. sqlite connection strings are named including the name of the data base they are connecting to
57. in new forms that only have sqlite connections if needing to create a new table create a new sqlite database and the desired table rather than using mysql existing database and messing up the form making it part mysql part sqlite
58. sqlite limitation of locking database not allowing to read and write at the same time is overcome using a load box in each form and changing its text to loaded or not loaded at the appropriate locations
59. in sqlite to reduce need to use load box dont alter controllers within read functions. only after the connection is closed to not trigger controller change function that will try to access the same database. instead get values from read assign to variables and only once the connection is closed make the controller text or such alteration
60. in the case of running a code for the first time and getting an error first thing to do is read it from the top looking for typos. on finding the first typo fix it and run the code again as the first one is likely to be the only one. if keeping on getting errors repeat till entire code is read and only then start debugging conducts to locate the cause of the error
61. side bar form always having a timer running and an hourly interval that backup all sqlite databases copying them to an incrementing folder
62. polymath home load resets a cointainer marking whether a new debug file has been created. if it hasent a general function of write to debug file counts amount of files in folder and creates a new increment. side bar displaying the greatest increment with a load button which creates a new file on right mouse click
63. on debug attempt number 10 if there is a wait time within code such as having to wait for loop to arrive at a certain point try to minimize this wait time like replicating the faulty conditions within the first loop
64. only on really rare occasions can a routh patch be used to fix a coding bug. meaning not knowing why the bug happens. not fixing the direct cause yet using an if condition in case it happens to tell the code to keep going. only if too much time is spent debugging without success or if predicting rewriting the code in the future or predicting managing to debug the code in the future for some reason not available in the present
65. in complicated codes when having trouble locating which part is being skipped due to if statement or such spread incrementing markers writing to debug file along code
66. default button to create in the creation of every new form is a test button. meant to remind me in case of a long execution and struggling with a debug to use the test button to create a costume abbreviated execution
67. monthly reminder if project wont run after adding sqlite connection without error it might be error in relative path of sqlite database
68. if i waste a bunch of time doing debugging and im afraid it may happen again leave a comment in the code near the area i would check if it happens again as to what the problem might be
69. on giving a drop down additional functionality like when right clicking it or double clicking it give it a distinct fill like a gray fill to let me know
70. it is important to create visual studio form controllers in certain order accounting for wanting to go from one to the next using tab. this order should also be reestablished if adding a new controller post creation
71. add are you sure? to buttons of long loads in case of a misclick
72. incrementing part of variables only as suffix to allow search replace in case i want to add variation to its name such as _picture
73. try to fear that a debug that is going to take while such as converting all images to low res might have nothing to do with the problem and will be all for nothing and so make damn sure its the issue. Such as by turning images load off and seeing if bug remains
74. switching variable from local to global delete declaration of the local so i dont miss refrences
75. learn things when you need to know them to solve a problem not before
76. when creating controllers in visual studio bunch together the controllers by differnt properties such as a paragraph of all the sizes declarations or positions to easily see them in relation to one another rather than each time defining all the properties for each controller separately
77. dont asisgn values to variables when declaring them. this will occasionally result in extended debugging not noticing there is an error in value retrieval
78. controllers creation in visual studio is done using a function per each passing paramters of their properties rather than each time writing 10 lines to create a button
79. by lesson of adding system insertion when adding task always think while writing code what a pain its going to be if i need to make an edit later on and write in accordance
80. on using a loop to create and lunch a costume made pormpt always place the show at the end of the loop so first prompt doesnt show before some function gets decalred
81. the reason code isnt to be developed in excel is because once it reaches a certain level of complexity it stops working and there is no fixing it
82. dont start any title with a number. it leads to errors in unforseen programming uses
83. in mysql updates and insertion in case of failure alert data not inserted + query string
84. when doing mysql functions always write query to a debug file to be able to review if debugging is required
85. if using a prompt on mysql function to notify me data has been inserted also metion the name of the database and table where it was inserted to
86. when using visual studio and removing a loop first find itsclosing bracket delete that and only then scroll up and delete the loop line to prevenet fumlbing looking for the closing bracket to delete afterwards
87. when using visual studio and removing a loop first find itsclosing bracket delete that and only then scroll up and delete the loop line to prevenet fumlbing looking for the closing bracket to delete afterwards
88. load grid in c sharp visual studio using a general function that gets the datatable in a single line of code
89. prevent visual studio controllers flashing by hiding or decreasing size of form to 0 till loaded
90. before manual task i feel will take 10 minutes or longer consider whether making a code to do it will take less time than the task itself also leaving me with the code to do it swiftly next time. if so make the code. also make the code even if it will take longer than the task if i think the code will be highly useful giving me a return of value on the time
91. on correcting a line of code that i remember i used in more than one place in project do search for entire solution and correct them all
92. when writing down a marker to file attempting to locate a bug also have it write a randomly typed number for me to later easily locate the marker and disable it looking for that number in entire project
93. create temp folder for output and temporarily change path to that temp folder over excusing not testing code to not make a mess in the real folder
94. when choosing to write out specific code over using a loop. use one base for specific such as position and size of a primary control and specifiy all others in relation to it so i can alter all of them by a single code edit of the specifics of the base
95. on creating a control as a gird by loop use the count of the list of the control to refrence position
96. creating code always look ahead to exceeding capacities such as total controllers creating errors even if seemingly 100 years in the future to avoid getting there early and having to debug looking for the issue
97. before using google to look up answers for coding questions try chatgbt
98. to minimize code operations in visual studio rather than running code on every timer tick event run it every several seconds checking if seconds remainder when divided by 2 or 3 or such is zero
99. in mysql and sqlite avoid using column names containing programming language words such as limit. instead try to use synonyms or even translation of the word you want to another language. to use these words in column may bring unforeseen debugging in the future
100. if adding a paramter to an existing visual studio c sharp function always add it in the end. to add it in the middle or where it makes sense may bring to hours of debugging as i go over all the existing uses of the function inserting a value. alternatively create a new function called the same only with an incremented suffix indicating a more advanced version